Graphical Design Verification Environment Generator

ABSTRACT

A graphical tool creates design-verification environments. The tool includes a graphical environment builder that allows for the drag and drop addition of verification IP (“VIP”) modules to a graphical verification environment. The tool assigns connector signals associated with source code that simulates a connection between a VIP module and the device under test (“DUT”). The tool learns which connection signals are suitable to connect a VIP to the DUT and facilitates selecting of the suitable signals in the environment development process. The tool converts the graphical environment to source code that can be executed to simulate testing on the DUT. The tool also allows a user to navigate between view modes that display the verification environment graphically, and that display the source code associated with components of the verification environment.

RELATED APPLICATION

This application claims the benefit of U.S. Provisional application No.61/978,899 filed Apr. 13, 2014, titled “Methods, Circuits, Devices,Systems and Associated Computer Executable Code for Simulation BasedVerification Testing of an Integrated Circuit Design,” which isincorporated by reference in its entirety herein.

TECHNICAL FIELD

The present disclosure generally relates to electronic designverification testing. More specifically, the present disclosure relatesto systems and methods that create a verification environment via agraphical interface that simulates testing on an integrated circuitdevice.

BACKGROUND

Designing an integrated circuit involves considering factors that relateto electronic circuits, analog functions, logic, and otherfunctionality. For example, before it is released for production (i.e.,tape out), an integrated circuit device may undergo a series ofsimulation tests to ensure that the integrated circuit will operate asplanned. These simulation tests can be used to find bugs, mistakes, orother issues with the device. This simulation is referred to as designverification.

Design verification can provide several benefits. For example, designverification can reduce the need for tape out processes that can beexpensive and time consuming, which can prolong the time it takes tobring the device to market. That is because the design verificationenvironment can simulate and/or emulate the bugs and other problems thatwould otherwise be found by the end customers, thereby allowing thedesign team to fix the problems before significant time and money issunk into production. Examples of devices that can benefit from theverification process include memory devices, communication circuitry,modems, smart phones, and field programmable gate arrays, among others.

This verification process can involve several engineers collaborating ina combined effort to check and test multiple circuits under variouscircumstances and operating environments. Universal VerificationMethodology (UVM) is a standardized protocol designed to help unifytechniques for verifying integrated circuit designs. UVM provides alibrary of automation features that are compatible with theSystemVerilog language and can include, for example, sequences and dataautomation features such as packing, copy, compare, and the like.

UVM provides a common framework for developing verification environmentsacross various platforms and circumstances. However, using UVM stillrequires manual coding, which can be a time consuming and laborioustask. This manual coding process can last from few working days to fewworking weeks. Manually written environments are also error-prone and donot always follow the methodology. Furthermore, their structure can varywithin the same project, which makes the maintenance, reuse andhand-over difficult.

SUMMARY

Certain embodiments of the present disclosure describe a computer and/ora computer processor configured to generate a design verificationenvironment. The design verification environment simulates testing on anintegrated circuit device under test (“DUT”). The processor is incommunication with a user interface and a memory (e.g., an electronicstorage device such as a hard drive or a memory chip). The computerprocessor is configured to execute a series of programs, which maycollectively be referred to as a verification tool.

The programs of the verification tool include an environment buildingprogram that builds a graphical environment for display on the userinterface. The graphical environment includes at least one verificationgraphic, and each verification graphic is associated with source codethat simulates a verification module interacting with the integratedcircuit device upon execution. The processor is also configured toexecute a signal connector program that assigns connection signals toverification graphics in the graphical environment. The connectionsignals are associated with source code that simulates a connectionbetween a verification module and the integrated circuit device uponexecution. The processor is also configured to execute a code generatingprogram that generates test simulation code. The test simulation codesimulates operation of the integrated circuit device when it isexecuted, for example, by a simulator or simulation program. The memorymaintains an available verification module array that includes at leastone verification graphic.

In operation, the environment building program displays the availableverification module array and the graphical environment via the userinterface. The environment building program also adds verificationgraphics to the graphical environment in response to receiving acommand, such as an add-graphic input signal, from the user interface.The signal connector program assigns a connection signal for eachverification graphic of the graphical environment. The code generatingprogram generates a test simulation code in response to receiving acommand, such as a generation input signal, via the user interface. Thetest simulation code is based at least in part on the source codeassociated with each verification graphic of the graphical environmentand each connection signal generated by the signal connector program.The test simulation code is formatted for execution on a simulator thatcan simulate testing of the integrated circuit device.

Certain embodiments of the present disclosure also present methods forcoding a verification environment that can be used to simulate testingon an integrated circuit DUT. The methods are be carried out by acomputer having a memory, a processor, and a user interface. In someexamples, the method can be carried out by the computer and/or thecomputer processor executing the programs described above. The methodinvolves displaying a graphical environment model on a user interface inresponse to receiving a command, such as an input signal via the userinterface. The graphical environment model includes a device graphicthat represents the DUT. The method also involves maintaining anavailable verification module array on the computer memory. Theavailable verification module array includes at least one verificationgraphic that corresponds to source code representing a verificationmodule. The method also displays at least one verification graphic inthe graphical environment model in response to receiving a command, suchas an add-graphic input signal, via the user interface. The verificationgraphic added to the graphical environment model is associated withsource code that simulates a verification model interacting with theintegrated circuit device upon execution. The method also assigns atleast one connection signal to each verification graphic in thegraphical environment. Each connection signal is associated with sourcecode that simulates as connection between the verification model and theintegrated circuit device upon execution. The method also generates atest simulation code in response to receiving a command, such as ageneration input signal, via the user interface. The test simulationcode is based at least in part on the source code associated with eachverification graphic in the graphical environment model and eachgenerated connection signal. The test simulation code simulatesoperation of the integrated circuit device upon execution. The methodalso formats the code, or transmits the test simulation code to asimulator that can simulate testing of DUT.

Some examples of the technology presented in present disclosure relateto computer readable storage mediums that are encoded with instructionsthat, when executed by a computer, cause the computer to perform aseries of steps that result in the coding of a verification environmentthat can be used to simulate testing on an integrated circuit DUT. Theinstructions can be carried out by a computer having a memory, aprocessor, and a user interface. In some examples, the instructions canbe carried out by the computer and/or the computer processor describedabove. And in some embodiments, the instructions represent source codethat executes the programs described above, including, for example, theenvironment building program, the signal connector program, the codegenerating program, the learning program, the navigation program, andthe verification graphic building program. The instructions execute todisplay a graphical environment model on the user interface in responseto receiving a command, such as a model display input signal, via theuser interface. The graphical environment model comprises a devicegraphic associated with source code that simulates the integratedcircuit device upon execution. The instructions also execute to maintainan available verification module array on the computer memory. Theavailable verification module array includes at least one verificationgraphic associated with source code that simulates a verification moduleinteracting with the integrated circuit device upon execution. Theinstructions also execute to display at least one verification graphicin the graphical environment model in response to receiving a command,such as an add-graphic input signal, via the user interface. Theinstructions execute to assign at least one connection signal to eachverification graphic in the graphical environment. Each connectionsignal is associated with source code that simulates a connectionbetween the verification model and the integrated circuit device uponexecution. The instructions also execute to generate a test code inresponse to receiving a command, such as a generation input signal or asave signal, via the user interface. The test code is based at least inpart on the source code associated with each verification graphic in thegraphical environment model and each assigned connection signal. Thegenerated test code simulates operation of the integrated circuit devicewhen it is executed, for example, by a simulator, or a simulationprogram.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing components of a computer system usedin accordance with at least one example of the present disclosure.

FIG. 2 is a block diagram showing the relationship of program modulesoperating on a processor in accordance with at least one example of thepresent disclosure.

FIG. 3 is a block diagram showing program modules interacting withlibraries and/or databases in accordance with at least one example ofthe present disclosure.

FIG. 4 is a block diagram showing the interaction of a navigationprogram with a user interface in accordance with at least one embodimentof the present disclosure.

FIG. 5 is an example of a screen shot presenting a user interfacedisplaying internal components of a verification graphic in accordancewith at least one example of the present disclosure.

FIG. 6 is an example of a screen shot presenting a user interfacedisplaying a graphical verification environment in accordance with atleast one example of the present disclosure.

FIG. 7 is an example of a screen shot presenting a user interfacedisplaying a graphical verification environment and a large objectsviewing window in accordance with at least one example of the presentdisclosure.

FIG. 8 is an example of a screen shot presenting a user interfacedisplaying a graphical verification environment and a library viewingwindow in accordance with at least one example of the presentdisclosure.

FIG. 9 shows example menus for adding custom code that are accessible ona user interface in accordance with at least one example of the presentdisclosure.

FIG. 10 shows example of a user interface that allows for viewing sourcecode associated with a particular object associated with the graphicalverification environment in accordance with at least one example of thepresent disclosure.

FIG. 11 is an example of a screen shot presenting a user interface thatallows interaction with a code editing function in accordance with atleast one example of the present disclosure.

FIG. 12 is an example of a screen shot presenting a user interface thatallows a user to connect verification signals with DUT signals inaccordance with at least one example of the present disclosure.

FIG. 13 shows the screen shot of FIG. 12 with certain recommended DUTsignals highlighted in accordance with at least one example of thepresent disclosure.

FIG. 14 is an example of a screen shot presenting a user interface thatallows a user to apply all previously suggested connection signals tothe graphical environment in accordance with at least one example of thepresent disclosure.

FIG. 15 is a flow diagram of a method for coding a verificationenvironment in accordance with at least one embodiment of the presentdisclosure.

DETAILED DESCRIPTION

The present disclosure describes embodiments of computer implementabletechniques or programs (hereinafter the “verification tool”) that allowfor efficient and convenient production of design verificationenvironments when compared to manual coding techniques. Certainembodiments of the verification tool can create design verificationenvironments that have a uniform structure, and that are compatible withAccellera guidelines for UVM. The code that the verification toolgenerates can be scalable and tested with a cross-simulator.

Creating a design verification environment can involve a lot of manualcoding, and can be a very labor intensive process. Generally, whencreating a design verification environment, a user will first create oneor more verification Intellectual Property (“VIP”) interfaces that driveand monitor signals that are connected to and/or transmitted to and fromthe DUT. The VIPs have interfaces that represent signals and otherinteractions with the DUT.

Next, the user can manually connect the DUT signals to the VIPinterfaces. This is done by way of generating code that represents theseconnections.

Next, a developer will create files and classes in accordance with theUVM standard so that the environment is scalable and can be compiled. Adeveloper can then connect all the transaction level modeling (“TLM”)ports and callbacks that reside in the VIPs to the environmentscoreboard (i.e., a reference model or a “golden model”), which notifythe scoreboard on any bus activity. The scoreboard can monitor theinputs, outputs, and the configuration of the DUT, predict the expectedoutputs, and issue notifications such as error messages when the actualbehavior does not match the expected behavior. The developer can thencreate scripts for running the environment using the preferablesimulator. Finally, the developer documents the entire environment. Thismanual process can be very labor intensive and time consuming.

Some design verification environment building tools employ templategenerators to help with generating environments. Template generators cancreate appropriate files in response to a name provided via user input.While these template generators can be helpful and more efficient thanmanually coding the files, the resulting templates may still requirelots of manual work to run properly. Further, these template generatorsdo not create a full verification environment. Rather, the templategenerators simply create VIPs. Thus, these template generators do notinstantiate the VIPs, nor do they facilitate in connecting the VIPs tothe DUT.

Templates generators may be packaged and shipped with simulators,thereby aiming to provide a simulation device that can generate VIPs.However, as noted, these devices are limited, and cannot create acomplete configuration interface, coverage, or sequence. Furthermorethese generators do not document the VIPs that they generate, and thusdo not preserve valuable information that can be used to facilitategenerating future design verification environments.

Accordingly, while these template generators and related simulators mayprovide skeleton frameworks that can save time in the designverification environment generation process, they do not address theproblem of creating a verification environment with its underlying VIPsand the connection to the DUT.

The presently described technology provides programs and methods thatcan add verification modules (which can be, for example, VIPs) to agraphical environment using a drag-and-drop operation. This feature canalleviate the cumbersome manual coding process for VIPs, and in someinstances every VIP, in an environment. The verification tool providesverification modules (e.g., VIPs) that can be embedded, packaged, and/orshipped with the verification tool software, or created by it.

These verification modules can implement a well-known or standardizedstructure so that the modules can be easily parsed by the verificationtool. This feature allows the verification tool to produce coding thatcan instantiate and connect the verification modules embedded in theverification environment.

In some aspects, the environments that the verification tool creates arefully compliable by common simulators (e.g., IUS, VCS and Questa).Further, the environments can be scalable, so that a user can embed theenvironment in a cluster environment or a full-chip environment. Theenvironments can also include many, most, or even all of thenotifications needed to simulate interactions between the verificationmodules (e.g., VIPs) and a scoreboard by way of TLM ports and callbacks.

In some examples, the DUT may comprise several modules, at least one ofwhich is verified using a block level verification approach. An operatorcan integrate the existing environments in order to maintain knowledgeof which of the DUT modules may be causing a problem. This process ofintegrating manually coded environments can be cumbersome and involveconnecting the block-level environments to the signals within the DUT.However, the present verification tool can include a connectivitydatabase so that a computer or computer processor can automaticallyperform the interface connection process, for example, by applying theknown hierarchy of the module within the DUT. Further, in some examples,the verification tool can also instantiate the environments in a mannersimilar to the way that the tool instantiates VIPs in block levelenvironments.

In certain embodiments, the verification tool employs a wizard, or asignal connector program, to automatically connect and/or facilitateconnecting the verification module signals (e.g., VIPs signals) to theDUT. The signal connector program can assign connection signals, orotherwise connect signals associated with verification modules/VIPs withsignals associated with the DUT. The signal connector program can alsomaintain and update a database of previously connected signals, suchthat the more environments that the verification tool creates, thebetter the tool becomes at automatically assigning and/or recommendingconnections. The verification tool can be configured to parse andpresent the DUT inputs and outputs, as well as all the verificationmodule/VIP interfaces and associated signals.

Unlike other techniques that require these connections to be manuallyperformed by one or more verification engineers, and typically by a teamof verification engineers, the presently described verification tool canperform these functions automatically based on information learned whilebuilding previous verification environment. Additionally and/oralternatively, the presently described verification tool can suggest orrecommend connections so that a user can still assign the connectionsmanually, but with the assistance and guidance of the verification toolprogram. For example, the verification tool can list the recommendedconnections in a tree-view fashion, such that each interface can beexpanded or collapsed while presenting its signals. The manual codingand connection work can be exhaustive on the engineer, as it can involvenavigation through each interface in order to extract its signals. Thisexhaustive work leaves the engineer susceptible to leaving some signalsunconnected or partially connected. It also leaves the engineersusceptible to copy and paste errors, or for accidental connection ofthe same signal more than once.

The presently described hardware, software, methods, and techniques alsoprovide for easy navigation through the environment components,properties and source code. This is provided because of the verificationtool's ability to filter, highlight and perform changes without deeplydiving into an existing code. A user of the verification tool can haveall, or virtually all tools helpful to build an environment in one placeaccessible via a single interface. In this manner, the user may not needto navigate through many folders and files, searching for some piece ofcode to build an environment.

Certain embodiments described herein are methods, circuits, devices,programs, systems and associated computer executable code for simulationbased validation testing of an integrated circuit design, which circuitdesign may be referred to as a DUT. The DUT can include analog circuitsegments, digital circuit segments, or both. Some embodiments present acircuit design testing platform that simulates operation and assessperformance of the DUT across a range of operational conditions and/orin response to a variety of external signaling sequences, sequencepermutations or scenarios.

External signaling to the DUT during validation testing can be generatedduring simulation by one or more verification modules, which can be, forexample, VIPs, ancillary circuit models, or the like. The verificationmodules can link to the DUT simulation model. The verification modulescan be predefined, as part of an array (or library) of verificationmodules, or a blank verification module. In this manner, theverification tool can automatically generate verification modules basedvia a graphical environment building program in response to a usercommand or input via a user interface.

The verification tool can link the verification modules to the DUT modelvia the graphical environment, which can also be linked to a testsimulation code generator. The DUT together with the verificationmodules establish a design verification environment. The verificationtool can also link or integrate one or more design verificationenvironments and/or additional DUTs via the environment builder programand/or the test code generating program.

During testing, the DUT model operation can be simulated under the sameoperational conditions, for example, clock frequencies, configurationvalues, power modes, clock skews, negative testing, reset duringoperation, overflow, underflow, random delays in the inputs,back-pressure, random data sizes, or the like. As part of a given DUTtest, the verification tool can alter the initial operational conditionsof the DUT. Prior to testing, the code generator can generate orregenerate the test simulation code, replacing one verification modulewith another verification module from the array of availableverification modules (or VIP library). For example, the code generatorcan combine source code that is affiliated with various modules of agraphical environment in response to receiving a command from a user viaa user interface. Additionally, the verification tool can replace and/orpartially replace the verification module while maintaining and/orpreserving code that a user can add via a user interface.

Other embodiments of the present disclosure describe verificationcheckers. The verification tool can automatically configure a checkerbased on a predefined protocol or algorithm (for example using C orMATLAB). A checker can be, for example, a comparator or a componentresponsible for verifying that the DUT outputs are operating asexpected. In some examples, checkers can be integrated within theenvironment scoreboard.

Additional embodiments can also present a library of predefinedenvironment architectures that a user can select to be tested on theDUT. These predefined environment architectures may be characterized sothat most DUTs are included within at least one architecture. Thepredefined environment architectures can include, for example, expectedsimulation inputs to the DUT and may automatically configure thechecker/scoreboard/reference model. Automatic building of the checkermay include receiving parameters from a user using the user interface.

In some aspects of the technology described herein, the code generatingprogram includes both predefined verification environment architectures,blank architectures and/or user-definable architectures that can bedefined via a user interface. The code generating program can includedata item structure with user selectable variables, data types,randomization selection and more.

The code generating program can also access and/or include one or moreverification modules that include a library of available verificationmodules (i.e., a VIP library). The code generating program can include agraphical signal interface between one or more verification modules andthe DUT, and between one or more verification modules so that connectionbetween the modules of the graphical environment (e.g., graphicsrepresenting the verification module(s) and the DUT) provides aninteractive interface that is user friendly, thereby reducing errorsand/or mistakes through interaction with the interface.

Some embodiments of the verification tool employ a user interface thatallows a user to create a functional coverage model and test scenarios.Some embodiments provide a user interface that allows a user to addsystem verilog assertions from a built-in library. Some embodimentsprovide a verification plan, and techniques for creating a registerdatabase and code. Some embodiments also provide a verificationsimulator that includes a smart log that facilitates and/or enables postprocessing of simulation log files for efficient debugging of asimulation.

The presently described verification tool provides systems andtechniques that connect verification module interfaces to a DUT by usinga graphical interface. The verification tool employs drag-and-dropfunctionality via a user interface. In this manner, a user can select averification graphic, which represents a verification module (e.g., aVIP interface) from a list, or array of available verification graphics,and add that graphic to a graphical environment. This drag and dropfunctionality makes the building of the simulation and the reuseextremely simple, and can be done by users with even very limitedknowledge of the verification environment protocol. This also allows fora process that is much less error-prone compared to manual connections.

In some embodiments, the verification tool has machine-learningcapabilities and can suggest or recommend connecting signals thatconnect verification modules with the DUT in the graphical environment.This process can be performed initially by name (e.g., the verificationtool will try to pair the VIP signals and the DUT signals according totheir names and directions). Then, as the verification tool builds moreenvironments, the verification tool (e.g., via a learning program)collects data and improves its suggestion and/or recommendations.

The verification tool also provides a connectivity display where theverification module (e.g., VIP interface) represented by theverification graphics are listed separately. Further, the verificationtool can be configured to select a verification module signal/DUT signalpair from a signal library (e.g., from a “connected” column) wheneversuch a pair is added to the graphical environment. This can help a useror environment developer to observe which signals are connected andwhich are not.

In some aspects, the verification tool can also make its own suggestionsand can automatically assign or connect verification module signals tothe DUT signals and shift them to the “connected” column. Theverification tool is also configured to parse the verification module(e.g., VIP), so that it can present the module's elements and alsoperform all the connectivity (e.g., instantiation, signals, TLM ports,callbacks) between the environment, the DUT and the selectedverification module (e.g., VIP).

Certain aspects of the described verification tool also include anavigation program that provides a graphical interface that facilitatesnavigation among various verification components (e.g., verificationmodules, features of the integrated circuit device, and/or designenvironments). This feature allows a user to display and edit existingcomponents at various levels, and in various formats (e.g., graphicalformats, source code formats, hybrid formats, etc.).

Referring now to the drawings, which demonstrate the various features,components, and operations of the verification tool in accordance withsome embodiments. FIG. 1 is a block diagram showing components of anexample computer system 2 configured to operate a verification toolconsistent with embodiments of the present disclosure.

The computer system 2 comprises a computer processor 10, CPU, computer,multiple processors, other such devices or combinations of such devices.In some aspects, the one or more processors can be implemented within asingle computer. In other embodiments, two or more processors can beimplemented in multiple devices that are coupled to communicate, forexample, through a network such as a local area network (“LAN”), widearea network (“WAN”), the internet, and/or another such network.

The processor 10 interacts with a user interface 20, which can include adisplay 22 and an input device 24. The display 22 can be, or caninclude, for example, one or more of a monitor, printer, touch screen,audio device, or other computer-related devices that present outputgenerated by the computer. The input device 24 can be or can include,for example, one or more of a keyboard, a mouse, a touch screen, amicrophone, a touch pad, or other computer-related devices that allow auser to interact and provide feedback with a computer.

In some embodiments, the display 22 and input device 24 can be the same,or at least intertwined. For example, the user interface 20 can includea touch screen that provides both the function of the display 22 and theinput device 24. Essentially, the user interface allows a user tointeract with the computer, and provides relevant information that thecomputer generates to the user.

The processor also comprises and/or accesses memory 30, which can be anelectronic storage device. For example, the memory 30 can include a harddrive, a thumb drive, an SD card (or micro SD card), RAM memory, orother storage media, or a combination of such memory. The memory 30 canalso be on the cloud or the internet, for example, and in someembodiments can include a network or other communication device thatallows information stored on the memory 30 to communicate with theprocessor 10, and the user interface 20.

The memory can be configured to store a number of files, libraries,databases, and other information and electronic data. For example, insome embodiments, the memory 30 is configured to store a VIP library 32(or a verification module library), which can be, or can include one ormore arrays of available verification graphics suitable for adding to agraphical environment. The verification tool can come pre-loaded withavailable verification models in the VIP library 32. Additionally and/oralternatively, the processor 10 can maintain, update, and/or modify theVIP library 32 either automatically, or in response to controls via theuser interface. For example, a user may update the VIP library 32 toinclude newly developed verification modules built using theverification tool.

The memory 30 can also include a signal library 34, which can be, or caninclude one or more arrays of available connection signals that simulatea connection between a verification module (e.g., a VIP) and a DUT. Insome embodiments, the signal library constitutes the VIP interface,listing all the connections and/or possible connections between a VIPand a DUT.

The verification tool can come pre-loaded with available connectionsignals in the signal library 34. Additionally and/or alternatively, theprocessor 10 can maintain, update, and/or modify the signal library 34either automatically, or in response to controls via the user interface.For example, a user may update the signal library 34 to include newlydeveloped connection signals created via the verification tool.

The memory 30 can also include a VIP/signal database 36, which can be orinclude one or more arrays of connection signals associated withverification graphics and/or verification models and correspondingsignals of an integrated circuit device. In some embodiments, theVIP/signal database 36 comprises a listing of pairs of connectionsignals and integrated circuit device signals that are known to besuitable connections.

In some embodiments the verification tool can come pre-loaded withconnection signal/circuit device signal pairs that are known to besuitable connections. Additionally and/or alternatively, the processor10 can maintain, update, and/or modify the database 36 eitherautomatically, or in response to controls via the user interface. Forexample, a learning program may update the database 36 to include newlyestablished connection signal/device signal pairs that have beensuccessfully and appropriately added to a graphical environment via theverification tool.

FIG. 2 is a block diagram showing the relationship of various circuitryand/or programs associated with the verification tool 100, in accordancewith some embodiments. As used throughout this application a “program”or “programs” can refer to circuitry configured to operate in, or inconnection with a computer processor or such devices. In someembodiments, the programs and/or circuitry can be implemented as astand-alone system in communication with one or more of the othercircuitry and/or interact with other programming. Further, theprograms/circuitry can be implemented through one or more computers,processors, databases, other memory or combinations thereof. In someembodiments, the programs/circuitry can comprise one or more processorshaving access to processor readable and/or computer readable memorystoring programming, code, firmware, executables, data, information orthe like, or combinations thereof. The programs can be stored in memory30 operated or executed, for example, on a processor 10 using thehardware and other components described above with respect to FIG. 1.

The verification tool 100 comprises an environment builder program 110or circuitry (or environment builder), which allows a user to build agraphical environment representing a design verification environment viaa user interface. The environment building program 110 builds agraphical environment for display on the user interface 20. An exampleof a user interface 20 displaying an exemplary graphical environment 300capable of generation by the verification tool 100 is presented in FIGS.6-8.

The graphical environment comprises at least one verification graphic310, and each verification graphic 310 is representative of averification module and is associated with source code that executes tosimulate the respective verification module interacting with theintegrated circuit device under test 320 (“DUT”). The verificationmodule can be, for example, a verification IP (“VIP”). The verificationgraphic 310 and/or the verification module can be associated with and/orinclude an interface comprising a series of signals that can interact orconnect with signals of the DUT 320.

The environment builder 110 is configured to present and build a designverification environment graphically, using blocks that represent sourcecode that execute to simulate operation of various verification objects.The environment builder 110 allows a user to add verification graphics310 to a graphical environment 300. The source code associated with theverification graphics 310, when executed by a simulator, can simulate averification module (e.g., a VIP) interacting with a DUT 320.

The environment builder 110 can present a menu that shows a list, or anarray of available verification graphics (an “available verificationmodule array”) that a user can add to the graphical verificationenvironment. The environment builder 110 can present the availableverification module array on the user interface 20 via a window that isconfigured to present such an array, for example. From this array, auser may select, via the user interface, one or more verificationgraphics 310 to add to the graphical environment 300. Thus the user candrag and drop the desired verification graphics 310 to the environment300. Each verification graphic is associated with source code thatrepresents, or simulates a verification module (e.g., a VIP interface)when executed. The verification module can thus comprise a listing ofconnection signals that represent signals and interactions with a DUT.

In operation, the environment building program 110 can display theavailable verification module array via the user interface 20. Forexample, the environment building program 110 can display a menupresenting a list of verification graphics 310 (each representing averification module) that can be added to the graphical environment 300.The environment building program 110 also adds verification graphics 310to the graphical environment in response to receiving a command, such asan add-graphic input signal, from the user interface 20. For example, inresponse to receiving a command from a user via the user interface toadd a graphic from the verification module array, the environmentbuilding program 110 will add the selected verification graphic 310 tothe graphical environment 300. In some aspects, the selectedverification graphic 310 can comprise a listing, or a library, ofprotocol signals that drive transactions with respect to the DUT 320 inaccordance with the verification module corresponding to the selectedverification graphic.

In some examples, the verification tool 100 includes a verificationgraphic building program, or a VIP builder 160 that allows a user tobuild a new verification graphic 310 that is not represented in theavailable verification module array. The verification graphic program160 thus generates a new verification graphic 310 representative of averification module in response to receiving a command, such as abuild-graphic input signal, via the user interface. In some aspects, theenvironment building program 110 can then add the new verificationgraphic 310 (representing a verification module) to the graphicalenvironment 300. In some aspects the verification graphic buildingprogram 160 will update the available verification module array toinclude each new verification graphic 310 (representing a verificationmodule) built with the verification graphic building program 160.

Using the verification graphic building program, a user can, forexample, define default parameters for the verification graphics, whichcan help in the future when using the same verification graphic withdifferent signals widths. In some embodiments the user can define thesignals in each verification graphic interface (which contains thesignals). For example, for each signal the user can: (1) define thesignal name, (2) define the signal width, (3) identify the driver (e.g.,master or slave), (4) set the initial value, and/or (5) provide a signaldescription. The user can also define the verification module data itemsand configuration, which may have fields that are similar to the fieldsfor the verification graphic interface, except the initial values andthe driver.

FIG. 3 is a block diagram showing the verification graphic builder 160interacting with the VIP library 32 maintained on the computer memory30. Once a verification graphic (representing a verification module) isbuilt via the verification graphic builder 160, the graphic can then beadded to the VIP library 32 so that the graphic can be added later toother graphical environments. In some embodiments, the verificationgraphic builder 160 can allow a user to access, edit, delete, orotherwise modify the verification graphics stored within the VIP library32.

Referring again to FIG. 2, the verification tool 100 also comprises asignal connector program 120, or a signal connector that assignsconnection signals to verification graphics in the graphical environmentto corresponding signals of the DUT. The connection signals areassociated with source code that when implemented simulate a connectionbetween one or more of the verification modules represented by theverification graphics added to the environment and the DUT. For example,the signal connector program acts to connect or correlate the signals ofone or more verification modules and signals of the DUT. For example,the signal connector program 120 can generate connection signals thatconnect protocol signals of the verification modules represented by theverification graphics with signals of the DUT.

In some examples, the signal connector program 120 selects one or moreconnection signals for each verification graphic 310 in the graphicalenvironment 300 from an array of available connection signals. The arrayof available connection signals can be maintained and/or stored, forexample, in the signal library 34 of the memory 30.

In some embodiments, the signal library 34 is an interface (e.g., a VIPinterface), identifying the signals suitable for connecting a particularverification module (e.g., a VIP) to a DUT. For example, eachverification graphic 310 can represent a verification module (e.g., aVIP) that comprises an array of available connection signals, and thesignal connector program selects one or more of these signals tosimulate a connection between the verification module and the DUT 320.

The signal library 34 can comprise a plurality of available connectionsignal arrays, or it can contain a single array, each array comprisingat least one available connection signal The signal connector program120 can then assign the selected signal as the connection signal betweenthe verification graphic and the DUT. In some embodiments, the signalconnector program 120 selects at least one connection signal from thearray of available connection signals based on the receipt of a command,such as a selection input signal, received via the user interface 20.For example, a user may select a particular signal from a menu thatpresents the array of available connection signals.

In some embodiments, the verification tool 100 includes a signal builderprogram 170 that allows a user to add verification signals to theinterface for each verification module. For example, the signal builderprogram 170 can provide an interface that allows a user to addconnection signals to an array of available connection signals for oneor more verification modules represented by a verification graphic. FIG.3 shows the signal builder 170 interacting with the signal library 34maintained on the computer memory 30. Once a connection signal iscreated, edited, modified, etc. via the signal builder 170, theconnection signal can then be added to the signal library 34 so that thesignal can connect verification graphics (or VIPs) to a DUT in latercreated graphical environments.

In some embodiments, the signal builder 170 can allow a user to access,edit, delete, or otherwise modify the connection signals stored withinthe signal library 34. In some embodiments, the signal builder programcan be a part of, or in communication with the verification graphicbuilder program 160. That is, the signal builder program 170 canfacilitate the building of new verification graphics by allowing a userto build, select, combine, or otherwise add connection signals to theinterface of the verification modules represented by verificationgraphics available to add to the graphical environment.

Referring again to FIG. 2, the verification tool 100 can also include acode generating program 130, or a code generator, that generates testsimulation code. The test simulation code can be executed by asimulator, for example, to simulate operation of the DUT within anenvironment represented by the graphical environment. The codegenerating program 130 generates a test simulation code in response toreceiving a command, such as a generation input signal, via the userinterface 20. The test simulation code is based at least in part on thesource code associated with each verification graphic of the graphicalenvironment and the source code associated with each connection signalassigned by the signal connector program 120. The test simulation codecan be generated in a format that can be executed on a simulator thatsimulates testing of the integrated circuit device.

In some aspects, the verification tool 100 also includes a learningprogram 150. The learning program 150 maintains a VIP/signal database 36of connection signals that are acceptable to connect certainverification graphics with the DUT. FIG. 3 shows the learning program150 interacting with the VIP/signal database 36 maintained on thecomputer memory 30. The learning program 150 updates the database 36 inresponse to each assignment of a connection signal to a verificationgraphic. For example, once a suitable connection signal is assigned toconnect a verification graphic to the DUT, the learning program 150updates the database 36 so that it includes the pairs of theverification graphic connection signals and DUT signals.

The learning program 150 is also configured to recommend a connectionsignal for each verification graphic added to the graphical environment.The recommendation is based on the information in the database 36 andthe particular verification graphic and corresponding DUT. For example,the learning program 150 can generate a recommended connection signal byconsulting the database 36 and recognizing a connection between theparticular signal of the verification graphic and a DUT in a previouslygenerated environment.

In some embodiments, the learning program 150 and/or the signalconnector program 120 displays the recommended connection signal forselection via the user interface. For example, the learning program 150can display one or more recommended connection signal to a user, orhighlight the recommended connection signal(s) among a list ofconnection signals, signifying a recommendation for a user to select thesignal for assignment to the verification graphic. The signal connectorprogram 120 can then select one or more connection signal for eachverification graphic from the array of available connection signals inthe signal library 34 based on a command received via the user interface20. For example, the signal connector program 120 can assign arecommended connection signal in response to the user interface 20transmitting a selection input signal, which can be generated inresponse to a user clicking on a particular object via the userinterface 20. Additionally and/or alternatively, the signal connectorprogram 120 can be configured to automatically select a recommendedconnection signal for at least one verification graphic.

Referring again to FIG. 2, the verification tool 100 can also beconfigured to execute a navigation program 140 that facilitatesinteraction with at least the environment building program 110, thesignal connector program 120 (connection not shown), the verificationgraphic builder program 120 and the code generating program 130 via theuser interface 20. FIG. 4 is a block diagram demonstrating operation ofa navigation program 140 in relation to the user interface 20. Thenavigation program 140 can be configured to control the display of thesource code associated with the graphical environment via the userinterface 20 in response to receiving a command, such as a displaycontrol input signal generated by a user via the user interface 20. Forexample, a user can toggle back and forth between a graphical view 25that displays the graphical environment on the user interface, and acode view 26 that displays the source code associated with the graphicalenvironment. In some embodiments, the user can also elect a hybrid 27view that displays both graphical components of the environment andsource code.

In some aspects, the navigation program 140 is also configured tocontrol the level of detail of the graphical environment displayed viathe user interface 20. For example, in response to receiving a command,such as a detail control input signal generated by a user via the userinterface, the navigation program 140 can allow a user to zoom in toview more detail regarding the makeup of the components and modulesadded to the graphical environment, and also to zoom out for ahigh-level view of the graphical environment.

In some embodiments, the navigation program 140 can allow for anintegrated editor (e.g., within the verification tool) to open and/oraccess the source code. Additionally and/or alternatively, thenavigation program can allow the source code to be opened and/oraccessed via an external editor as defined in the user preferences. Inthis manner, the user can have the ability to open a source file byselecting a specific file in the project view (e.g., in the right pane),or by double clicking on a graphical component or property.

Further, the navigation program 140 and/or other components of theverification tool can present information to a user in other manners.For example, hovering a mouse cursor over a module or property caninitiate a pop-up window that displays a snippet of code associated withthe module or property (a property can be, for example, a task, afunction, or the like). In some embodiments, the navigation program 140can highlight connections that provide more graphical information to theuser when navigating through the program. For example, the navigationprogram can present a user with a clocks-tree, which can presentinformation pertaining to which clocks are connected to whichverification modules, interfaces, content, etc.

In some embodiments, the navigation program 140 can be configured sothat a single click over a component will list (e.g., graphically) someor all of the properties of the component, including, for example, thevariables, tasks, functions associated with the component. In someexamples, the verification tool and/or the navigation program 140 canallow a user to update these properties from the same view withouthaving to open the source code. In still further examples, theverification tool can back annotate updates to the source code so thatthe changes will also be reflected in the user interface.

FIGS. 5-14 show screen shots of the verification tool 100 operating on auser interface 20 of a computer in accordance with embodiments of thepresent disclosure. FIG. 5 is an example of a screen shot presenting auser interface 20 operating a verification graphic builder program 160of the verification tool 100. The user interface 20 displays internalcomponents of a verification graphic 210 (e.g., a VIP). Via the userinterface 20, a user is allowed to add properties, signals, and otherfeatures to the verification graphic 210, which can represent averification module (e.g., a VIP), and be added to the graphicalenvironment via the environment builder program 110 of the verificationtool 100.

The user interface 20 includes a create tab 220, which allows a user tobuild, edit, modify, delete, or otherwise configure various verificationgraphics 210. The user interface 20 also includes a debug tab 230 whichcan present a user with another interface that allows for debugging ofparticular aspects of the verification graphic 210. In some embodiments,the user interface 20 can also include a documentation tab which canpresent the project documentation when selected by a user. The projectdocumentation can be displayed in HTML format, for example. Thedocumentation can be generated by the verification tool upon thegeneration of a verification graphic or a graphical environment, forexample.

The interface can include a modular window 240 that includes propertiestab 242 and a library tab 244. The properties tab 242 allows a user toview, add, and edit various features of the verification graphic 210,and the library tab 244 allows the user to view and access the signallibrary 34 and/or a VIP library 32 and access signals and other featuresto add to the graphical environment.

The user interface 20 can also include a project window 250, whichprovides an overall outline of the graphical environment project. Viathe project window 250, the user interface 200 provides access to thenavigation program 140, thereby allowing the user to view variousportions of the graphical environment in greater or less detail, and toselect a mode by which the environment is viewed (e.g., in a graphicalview 25, code view 26, hybrid view 27, or the like).

FIG. 6 is an example of a screen shot presenting a user interface 20operating the verification tool 100 to display an exemplary graphicalverification environment 300 in accordance with embodiments of theverification tool 100. The graphical environment 300 comprises multiplemodules, including several verification graphics 310, which can be, forexample VIPs that have an interface comprising signals. The verificationgraphics 310 can each be associated with source code that is configuredto execute on a simulator, and, when executed, simulates the interactionof a verification module (e.g., a VIP) with the DUT 320.

The graphical environment 300 also includes a DUT 320, which canrepresent an integrated circuit device intended to be used in testing.The DUT 320 is connected to multiple verification graphics 310 viaconnections 390. The connections 390 can be assigned by the signalconnector program 120 of the verification tool 100. Via the userinterface 20, a user can click on an arrow representing a connection 390and be presented with a menu, window, or other interface that allows theuser to select and assign connection signals that connect the signals ofthe verification graphics 210 with the DUT 320. The graphicalenvironment 300 also includes a scoreboard 330, which can be a referencemodel that monitors bus activity of the verification modules.

FIG. 7 is another screen shot of the user interface 20 operating theverification tool 100 to display an exemplary graphical verificationenvironment 300 and a large objects viewing display 246 in theproperties tab 242. The large objects viewing display 246 allows a userto drill down into large objects (e.g., verification graphics,environments, a DUT, a scoreboard, etc.) in the graphical environment300. A user can drill down into large objects either for purposes ofviewing the objects or to edit/modify the objects. The user can drilldown by selecting the object in the display 246 with a mouse, whichselection can cause the object to display in a new window expanding fromthe modular window 240.

FIG. 8 is a screen shot of a user interface 20 operating theverification tool 100 to display an exemplary graphical verificationenvironment 300 in which the library tab 244 selected to display alibrary viewing window 248. The library viewing window 248 can providean interface allowing a user to access the VIP library 32, the signallibrary 34, the VIP/signal database 36, or other libraries and/ordatabases. In this manner the user can select verification graphics froma list of graphic names 311 to add to the graphical environment 300.

FIG. 9 shows configurations of an object display 247 that can beaccessible, for example, via the properties tab 242 of the window module240 of the user interface 20. The object display 247 provides a menuthat allows a user to add custom code to the design verificationenvironment.

In some embodiments, the user can access an add custom menu 260, whichwill allow the user to add objects to the object display 247. To modifycustom code, a user can click on the add custom icon 262 and select themethod item 261, This selection will add a new method 263 to the objectdisplay 247. Likewise, a user can add a function, a counter, a task,clocking blocks, or other functionality to the object window, each ofwhich can be used to add, or modify the graphical environment 300 viathe user interface 20. The new method 263 can comprise custom sourcecode that can be entered by the user. The source code can be executed tosimulate a number of features relating to design verificationenvironments, including but not limited to VIPs, connection signals, DUTsignals, scoreboards, or the like.

FIG. 10 illustrates another feature of the object display 247 presentedby the user interface 20. In FIG. 10, a cursor 239 hovers over an object255 in the object display 247. This process causes a code preview window270 to display to the right of the object 255. The code preview window270 shows the source code associated with the object. In this manner auser can review the source code associated with objects.

In some embodiments, a user may be able to step into and add, modify, ordelete source code via a code editing platform. For example, FIG. 11 isa screen shot of the user interface 20 operating a code editing feature400 of the verification tool 100. In the context of the code editingfeature 400, the verification tool 100 displays the properties tab 242,which shows the entities extracted from the currently edited file. Theselected entry 267 of the object display 247 is highlighted. When a userselects an entry (e.g., by clicking on that entry with a mouse) theverification tool 100 can automatically display the code associated withthat entry in the code editor 400. In this manner a user will then beable to edit, add, delete, or otherwise modify the code associated withthat entry.

In some embodiments, the user can change or modify the source code usingthe code editing feature 400, or through an external editor program, forexample. In this manner, the verification tool can parse and presentchanges that are opposed by the user in the source code via the userinterface. In some aspects, the verification tool can include a linterthat can validate, verify, and/or debug any code that the user adds inthis manner.

FIG. 12 is a screen shot of a user interface 20 operating the signalconnector program 120 of the verification tool 100. The user interface20 comprises a connection display 410, which shows an array of availableconnection signals 434 in a VIP signal window 420, and an array ofavailable DUT signals 435 in a DUT window 440. The signals displayed inthe VIP signal window 420 can be associated with verification graphics310 added to the graphical environment 300. The signals can be, forexample, the signals stored in the signal library 34 associated withthat particular verification graphic 310. A user can select a signalfrom the VIP signal window 420 and a corresponding signal from the DUTwindow 440, and assign, or pair the signals with one another, byclicking on the connect button 450.

In some embodiments, the learning program 150 will recommend signals topair with one another and display the recommended signals via the userinterface 20. The recommendation can be based, for example, oninformation stored in a database that identifies pairs of signals thathave been connected in previously built environments. FIG. 13 shows thescreen shot of FIG. 12 with certain recommended DUT signals highlighted.For example, upon selecting a signal from the VIP signal window, thelearning program may highlight one or more signals from the DUT window440, the highlighted signals representing recommended signals.

In some aspects, the learning program 150 can highlight the recommendedsignals automatically. Alternatively, the learning program 150 canhighlight the recommended signals in response to an instruction from auser via the user interface 20. For example, the user can select a VIPconnection signal 480 and click on the first suggest button 455 tohighlight the recommended DUT signal(s) 482 corresponding to theselected VIP connection signal 480. Likewise, a user can select a DUTsignal 482, and click on the second suggest button 457 to highlight therecommended VIP connection signal.

The learning program 150 can recommend the signals based on informationin the VIP/signal database 36 relating to signals that were previouslysuccessfully assigned to one another or by pattern matching, forexample. Connected signal window 436 can display the VIP/signal database36, thus displaying pairs of signals that are currently applied. In someembodiments, the learning program 150 can automatically assign and/orpair the signals without requiring feedback from a user.

FIG. 14 is a screen shot of a user interface 20 operating theverification tool 100 to view the signal pairs that are currentlyapplied to a graphical environment 300. An auto signal interface window490 allows a user to review the suggested connections, and allows a userto check or uncheck all suggestions recommended by the learning program150 and apply them to the graphical environment. In this view a user isable to see all the suggested connections recommended by the learningprogram 150 as they pertain to the graphical environment underconstruction. The user can choose to apply, or refuse the recommendedconnections via this interface.

Certain embodiments of the present disclosure also present methods forcoding a verification environment that can be used to simulate testingon an integrated circuit DUT. The methods can be carried out by acomputer, or a computer processor executing the programs of theverification tool 100. The computer carrying out the method can have amemory, a processor, and a user interface. In some examples, the methodcan be carried out by the computer and/or the computer processorexecuting the programs described above.

FIG. 15 is a flow diagram of a method 500 for coding a verificationenvironment. The method 500 includes the steps of providing a VIPlibrary 505 and providing a signal library 510. The VIP library can bean array of available verification graphics that can be added to agraphical environment. The signal library can be an array of availableconnection signals that represent interaction of a verification modulewith a DUT. In some embodiments, the signal library includes an array ofavailable connection signals for each verification graphic added to thegraphical environment.

In some embodiments, steps 505 and 510 can further include maintaining,updating, modifying, adding to, or deleting from the VIP and/or signallibrary. The VIP library and the signal library can be maintained, forexample, on a memory device that communicates with the computer and/orthe computer processor. In some embodiments, steps 505 and/or 510 can bedone automatically by a verification tool, such as the verification tooldescribed herein. For example, the verification tool can parse theinterface and update, modify, and/or maintain the VIP/signal librariesas a user adds a verification graphic to the environment. The method 500can also include maintaining a VIP/signal database that keeps a log ofconnection signals that have been applied to connect certainverification graphics to certain DUTs in previously prepared graphicalenvironments.

At step 515 a DUT is added to the graphical environment. The DUTrepresents an integrated circuit device to be tested by a simulationprogram according to the parameters established by the graphicalenvironment. The DUT can be represented by a device graphic displayed onthe user interface.

Step 520 involves displaying a graphical environment model on a userinterface in response to receiving a command, such as an input signalvia the user interface. The graphical environment model can include thedevice graphic representing the DUT selected in step 515.

At step 525, a verification graphic (e.g., a VIP graphic) is added toand displayed via the graphical environment model. The verificationgraphic can be added in response to receiving a command, such as anadd-graphic input signal, via the user interface. In some embodiments,the verification graphic added is selected from the array of availableverification graphics maintained in the VIP library. In otherembodiments, the verification graphic added is new and is created usinga verification building program. The verification graphic added to thegraphical environment model is associated with source code thatsimulates a verification model interacting with the integrated circuitdevice upon execution.

At step 530, the method 500 assigns at least one connection signal toeach verification graphic in the graphical environment. Each connectionsignal is associated with source code that simulates as connectionbetween the verification model and the integrated circuit device uponexecution. The connection signal can be selected from an array ofavailable connection signals maintained in the signal library. In someembodiments a learning program recommends connection signals forconnecting to the DUT. Further, in some embodiments, the learningprogram automatically assigns a connection signal to a verificationgraphic without receiving feedback or input from a user.

At step 535, the method 500 can involve updating the VIP/signal databasewith the connections signals that were applied in step 530. In thismanner, the VIP/signal database maintains a record of suitableverification graphic/DUT connections, and can be referenced to suggestrecommended connections while building future graphical environments.

Step 540 involves generating test simulation code based on the graphicalenvironment. For example, in response to receiving a command, such as ageneration input signal, via the user interface, a code generatingprogram generates simulation code that is based at least in part on thesource code associated with each verification graphic in the graphicalenvironment model and each generated connection signal. The testsimulation code can be configured to simulate the operation of the DUTwithin a design verification environment represented by the graphicalenvironment when executed. In some embodiments, method 500 also formatsthe code so that it is suitable for simulation on a particularsimulator.

The method 500 can also include the step 545 of sending or transmittingthe test simulation code to a simulator that can simulate testing ofDUT. The transmission can occur by formatting the source code onto acomputer readable storage medium and delivering the source code to acomputer configured to operate the simulator. In some embodiments thesource code can be transmitted via the internet, email, or another modeof electronic communication.

At step 550, the method 500 includes verifying the DUT in a simulator byexecuting the test simulation code. In some embodiments, the simulatorcan be operated on the same machine, or machines that generated the testsimulation code. Alternatively, the simulation can occur on othermachines that were not involved with the generation of the testsimulation code.

The presently described verification tool allows for the creation of averification environment using a graphical user interface. In someaspects, the verification tool can automatically generate a UVM-based,bug-free verification environments more efficiently and effectively thanif the environment were manually coded. The environments generated bythe verification tool can be, for example, cross-simulator, compilable,well documented, and scalable. Moreover, the verification tool cangenerate environments that have a uniform structure that eases themaintenance, reuse and hand over.

In some embodiments, the verification tool software can be pre-loaded,or originally provided with a VIP library that is preloaded withverification graphics that can be added to a graphical environment. Theverification graphics can be associated with source code that, whenexecuted represents a verification module (e.g., a VIP) that interactswith a DUT. The VIP library can be extended by the user, for example, byadding verification graphics to the VIP library using the verificationgraphic builder program of the verification tool.

In some embodiments, the verification tool allows for automaticinstantiating of all verification graphics (e.g., VIPs) in anenvironment. The verification tool also facilitates connecting theverification graphic TLM ports and callbacks to the scoreboard.

Some embodiments of the verification tool provide tools that allow auser to navigate through the environment between a graphicalrepresentation and the source code. The verification tool can alsoprovide a graphical wizard that connects VIPs interfaces to the DUTsignals.

In some embodiments, computers operating the verification tool canmaintain a database of all the previous connected signals within thecustomer premises, which can later be used to facilitate the matchingand/or connection process.

The verification tool can provide a clear, easy to understand view of adesign verification environment and its development status (e.g., howmuch of the coding building the environment has been completed). Theverification tool can also provide a clear view of how many signals havebeen connected to the DUT, which components of the environment have beenadded/completed, and which components are in progress.

The present disclosure describes preferred embodiments and examples ofthe present technology. Reference throughout this specification to “oneembodiment,” “an embodiment,” or similar language means that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment of thepresent invention. The embodiments shown in the drawings, if any, and asdescribed above are merely for illustrative purposes and not intended tolimit the scope of the invention. Moreover, those skilled in the artwill recognize that a wide variety of modifications, alterations, andcombinations can be made with respect to the above described embodimentswithout departing from the scope of the invention as set forth in theclaims, and that such modifications, alterations, and combinations areto be viewed as being within the ambit of the inventive concept. Thus,appearances of the phrases “in one embodiment,” “in an embodiment,” andsimilar language throughout this specification may, but do notnecessarily, refer to the same embodiment. All references cited in thepresent disclosure are hereby incorporated by reference in theirentirety.

1) A computer processor configured to generate a design verificationenvironment that simulates testing on an integrated circuit device, theprocessor being in communication with a user interface and a memory, theprocessor configured to execute: an environment building program thatbuilds a graphical environment for display on the user interface, thegraphical environment comprising at least one verification graphic, eachverification graphic associated with source code that simulates averification module having connection signals that interact with theintegrated circuit device upon execution; a signal connector programthat assigns connection signals of verification graphics in thegraphical environment to corresponding signals of the integrated circuitdevice, the connection signals associated with source code thatsimulates a connection between a verification module and the integratedcircuit device upon execution; and a code generating program thatgenerates test simulation code that simulates operation of theintegrated circuit device upon execution; wherein the memory isconfigured to maintain an available verification module array thatincludes at least one verification graphic corresponding to source coderepresenting a verification module, wherein the environment buildingprogram displays the available verification module array and thegraphical environment via the user interface and adds verificationgraphics to the graphical environment in response to receiving anadd-graphic input signal from the user interface, wherein the signalconnector program assigns a connection signal for each verificationgraphic of the graphical environment to the integrated circuit device,wherein the code generating program generates a test simulation code inresponse to receiving a generation input signal via the user interface,the test simulation code based at least in part on the source codeassociated with each verification graphic of the graphical environmentand each connection signal assigned by the signal connector program, andwherein the test simulation code is generated in a format for executionon a simulator that simulates testing of the integrated circuit device.2) The processor of claim 1, wherein the addition of a verificationgraphic includes selecting a verification graphic from the availableverification module array in response to receiving the add-graphic inputsignal via the user interface. 3) The processor of claim 1, wherein theprocessor is further configured to execute a verification graphicbuilding program, wherein the verification graphic building programbuilds a new verification graphic in response to receiving abuild-graphic input signal via the user interface, and wherein theenvironment building program adds the new verification graphic to thegraphical environment. 4) The processor of claim 3, wherein theprocessor updates the available verification module array to includeeach new verification graphic built with the verification graphicbuilding program. 5) The processor of claim 1, wherein the signalconnector program assigns a connection signal for each verificationgraphic of the environment model to the integrated circuit device, theconnection signal selected from an array of available connection signalsmaintained in the memory. 6) The processor of claim 5, wherein thesignal connector program selects at least one connection signal from thearray of available connection signals based on the receipt of aselection input signal via the user interface. 7) The processor of claim5, wherein the processor is further configured to execute a learningprogram that maintains a database of suitable pairs of connectionsignals and integrated circuit device signals, wherein the learningprogram updates the database in response to each assignment of aconnection signal with an integrated circuit device, and wherein thelearning program recommends a connection signal for each verificationgraphic based on the information in the database, the verificationgraphic, and the integrated circuit device. 8) The processor of claim 7,wherein the learning program displays the recommended connection signalfor selection via the user interface, and wherein the signal connectorprogram selects a connection signal for at least one verificationgraphic from the array of available connection signals based on thereceipt of a selection input signal via the user interface. 9) Theprocessor of claim 7, wherein the signal connector program automaticallyselects the recommended connection signal for at least one verificationgraphic. 10) The processor of claim 1, wherein the processor is furtherconfigured to execute a navigation program that facilitates interactionwith the environment building program, the signal connector program, andthe code generating program via the user interface, wherein thenavigation program is configured to control the display of the sourcecode associated with the graphical environment via the user interface inresponse to receiving a display control input signal via the userinterface. 11) The processor of claim 10, wherein the navigation programis further configured to control the level of detail of the graphicalenvironment displayed via the user interface in response to receiving adetail control input signal via the user interface. 12) A method forcoding a verification environment used to simulate testing of anintegrated circuit device, the method performed on a computer having amemory, a processor, and a user interface, the method comprising:displaying a graphical environment model on the user interface inresponse to receiving an input signal via the user interface, thegraphical environment model comprising a device graphic representing theintegrated circuit device; maintaining an available verification modulearray on the computer memory, the available verification module arrayincluding at least one verification graphic that corresponds to sourcecode representing a verification module; displaying at least oneverification graphic in the graphical environment model in response toreceiving an add-graphic input signal via the user interface, theverification graphic associated with source code that simulates averification model interacting with the integrated circuit device uponexecution; assigning at least one connection signal for eachverification graphic in the graphical environment to correspondingsignals of the integrated circuit device, each connection signal beingassociated with source code that simulates as connection between theverification model and the integrated circuit device upon execution;generating a test simulation code in response to receiving a generationinput signal via the user interface, the test simulation code based atleast in part on the source code associated with each verificationgraphic in the graphical environment model and each assigned connectionsignal, the test code simulating operation of the integrated circuitdevice upon execution, and transmitting the test simulation code to asimulator that simulates testing of integrated circuit devices. 13) Themethod of claim 12, wherein the step of displaying at least oneverification graphic in the graphical environment model includesselecting a verification graphic from the available verification modulearray in response to receiving an input signal via the user interface.14) The method of claim 12, wherein the step of displaying at least oneverification graphic in the graphical environment model furthercomprises building a new verification graphic via a graphic buildingprogram in response to receiving a build input signal via the userinterface, and further comprising the step of updating the availableverification module array with the new verification graphic. 15) Themethod of claim 12, further comprising the step of maintaining anavailable connection signal array comprising at least one connectionsignal associated with source code representing a connection between averification module and an integrated circuit device, and furtherwherein the step of assigning at least one connection signal comprisesselecting a connection signal from the available connection signalarray. 16) The method of claim 15, further comprising the step ofmaintaining in the memory a database of suitable pairs of connectionsignals and integrated circuit device signals, wherein the learningprogram updates the database in response to each assignment of aconnection signal with an integrated circuit device, and wherein thestep of assigning at least one connection signal further comprisesrecommending a connection signal based on the information in thedatabase of connection signals, wherein the recommended connectionsignal is based at least in part on the displayed verification graphicand the integrated circuit device. 17) The method of claim 16, whereinthe step of assigning at least one connection signal comprisesautomatically selecting the recommended connection signal. 18) Themethod of claim 12, further comprising the step of displaying sourcecode associated with the displayed graphical environment model on theuser interface model in response to receiving a display control inputsignal from the user interface. 19) The method of claim 12, furthercomprising the step of adjusting the level of detail of the graphicalenvironment model displayed via the user interface in response toreceiving a detail control input signal via the user interface. 20) Acomputer readable storage medium encoded with a set of instructionsthat, when executed by a computer having a memory and a user interface,cause the computer to: display a graphical environment model on the userinterface in response to receiving a model display input signal via theuser interface, the graphical environment model comprising a devicegraphic associated with source code that simulates the integratedcircuit device upon execution; maintain an available verification modulearray on the computer memory, the available verification module arrayincluding at least one verification graphic associated with source codethat simulates a verification module interacting with the integratedcircuit device upon execution; display at least one verification graphicin the graphical environment model in response to receiving anadd-graphic input signal via the user interface; assign at least oneconnection signal for each verification graphic in the graphicalenvironment to corresponding signals of the integrated circuit device,each connection signal associated with source code that simulates aconnection between the verification model and the integrated circuitdevice upon execution; and generate a test code in response to receivinga generation input signal via the user interface, the test code based atleast in part on the source code associated with each verificationgraphic in the graphical environment model and each assigned connectionsignal, the test code simulating operation of the integrated circuitdevice upon execution.